Hi there!
This is an interesting feature request, I can see the reasoning behind it, and it possibly would make sense to create such a distributed system for other applications as well 🤔.
However, I think it might be a better idea to make it more verbose, and follow the same path as https://github.com/grafana/helm-charts/tree/main/charts and create a separate hydra-distributed chart, as opposed to keeping it bundled in a single package, wdyt?

@Demonsthere Are there any concerns with the additional complexity required to update two charts for Hydra if we fork this one into a new chart? My concern is if there's multiple different charts it gets complicated to keep them all maintained. Maybe we could modularize this chart such that portions can be reused in the distributed version?

@Demonsthere If it wasn't clear, I'm totally open to doing this. Just looking for guidance to do it in a maintainable way.

Yeah, sorry it was just a busy week 😅
I think i am more in favour of a distributed chart, then overcomplicating the current one, as we would have to prepare options like different requests/hpa for each deployment :)

@Demonsthere No worries, thanks for the response, no rush.

Configuring the two deployments differently is actually supported in my current implementation by using the new deployment.admin and deployment.public options. These options act as overrides on top of the defaults specified in the deployment object.

But totally fair, definitely don't want to overcomplicate the chart. I can try making a separate chart.